bpo-45885: Don't un-adapt COMPARE_OP
when collecting stats
#31516
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current stats obscure the fact that "not followed by conditional jump" accounts for a significant portion of possible
COMPARE_OP
hits. This patch takes the same approach thatBINARY_OP
uses of only un-adapting the instruction when stats aren't being collected.New stats:
COMPARE_OP
specialization stats for COMPARE_OP family
Specialization attempts
https://bugs.python.org/issue45885